home *** CD-ROM | disk | FTP | other *** search
- Path: news.nyu.edu!schonberg!dewar
- From: dewar@cs.nyu.edu (Robert Dewar)
- Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.edu
- Subject: Re: ANSI C and POSIX (was Re: C/C++ knocks the crap out of Ada)
- Date: 8 Apr 1996 14:22:20 -0400
- Organization: Courant Institute of Mathematical Sciences
- Message-ID: <dewar.828987544@schonberg>
- References: <JSA.96Feb16135027@organon.com> <dewar.828757752@schonberg> <danpop.828819479@rscernix> <dewar.828879781@schonberg> <4k9qhe$65r@solutions.solon.com> <dewar.828936837@schonberg> <828964950snz@genesis.demon.co.uk>
- NNTP-Posting-Host: schonberg.cs.nyu.edu
- X-Newsreader: NN version 6.5.0 (NOV)
-
- With respect to read (Linux unusual behavior), Lawrence said
-
- "Both approaches meet the relevant standards and are correct. Only broken
- code has portability problems, but that's nothing new."
-
- Can you quote the relevant standard. No description of read I ever saw
- was detailed or precise enough to say what the requirements on the caller
- are.
-
- Lots of code is portable and broken, lots of code is (deliberately)
- non-portable and definitely not broken. Lots of code is carefully
- written to be portable, but runs into bugs in supposedly conforming
- implementations. Lots of code uses features that are useful, but for
- which no standard exists, and hence may run into portability problems.
-
- Equating portability with non-brokenness in general is naive. Even in
- an environment with a definite standard, writing portable code requires
- a lot more than just adhering to the letter of the standard!
-
-